Sequential node identification in multiple-compartment dispensing enclosures

ABSTRACT

A system for automatically assigning sequential identification values to networked nodes, such as accessory modules within a storage and dispensing enclosure. The system includes a host controller communicating with client controllers via both a shared, multi-drop communications bus and an initial segment of a daisy-chained, point-to-point communications bus. The host controller issues a token to a first client controller via the point-to-point bus, then queries the client controllers, receives a reply from the client controller having the token (associating that controller with a sequential identification value), and commands passing of the token, each via the multi-drop bus. The client controllers receive the token and query via the respective busses and, if that controller has the token, reply to the query via the multi-drop bus, as well as receive the command and, if that controller has the token, pass the token via the point-to-point bus to a subsequent controller.

The present application is directed to storage and dispensing enclosuresand, more particularly, to systems and methods in which networked nodes,such as door controls, dispensing modules, or other accessories housedwithin the enclosure, are automatically assigned a sequentialidentification value, such as incremented numerical value, withoutrequiring the manual assignment of such values to the individual nodes.

BACKGROUND

Storage and dispensing enclosures may include a plurality of internalcompartments for holding items to be dispensed, such as in multi-tiered,locker-like cabinets, and/or a variety of active dispensing units, suchas the “pushers” used in some vending machines to dispense individualitems, and/or a variety of passive dispensing units that track thepresence, withdrawal, and, potentially, return of items, such as inrack-and-bin and bin-in-drawer systems that dispense bulk parts orindividual tools (using bulk sensors such as load cells, countingsensors such as break beams, radio frequency identification sensors andradio frequency responsive tags attached to individual items or tools,etc.). The number, size and/or arrangement of the compartments, activedispensing units, and passive dispensing units may vary from enclosureto enclosure based upon an end user's practices and needs. In addition,such enclosures are significant capital equipment, and thusmanufacturers have begun to modularize compartment access controls,active dispensing units, and passive dispensing units for suchenclosures to allow for customized configuration and, potentially,reconfiguration of individual enclosures.

Such storage and dispensing enclosures require the installation ofaccessory components that are operatively connected to a controllerprogrammed to, e.g., control the operation of an access door based uponpayment or authorization, and/or control the operation of an activedispensing module based upon payment or authorization, and/or monitor apassive dispensing module so to provide an activity/audit trail.Potential accessory components include: compartment access controls suchas door locks and door position sensors; motors, solenoids, actuators,and switches for active dispensing units such as the aforementionedpushers; load cells, break beam emitters/detectors, and RFID sensors forpassive dispensing units such as the aforementioned bin systems; etc.Accessory components could also include annunciators, cameras,in-compartment environmental sensors, etc. Each of those accessorycomponents would conventionally be wired to a central controller thathas been configured to directly operate the accessory components.Alternately, some enclosures may include a master controller configuredto indirectly operate such accessory components via networked slavecontrollers provided in accessory modules. For example, U.S. patentapplication Ser. No. 14/466,040, published as U.S. Patent App. Pub.2016/0053514 and incorporated herein by reference in its entirety,discloses modular door assemblies providing door locks, door positionsensors, and annunciators (indicator lights) for controlling access toindividual compartments within an enclosure, where each modular doorassembly is directly controlled by an in-module (slave) microcontrollerand indirectly controlled by an in-enclosure (master) controller.However, and particularly in the case of highly customizable enclosures,installing and configuring such accessory modules can still be acomplex, time-consuming, and costly process because the networkedcontrollers should be logically associated with a particular compartmentor dispenser in a particular location within the enclosure.

SUMMARY

A sequential identification value that has a simple and easilycomprehended meaning to a human operator, who could be responsible forthe initial configuration of an enclosure, the in-the-field repair of amalfunctioning enclosure, or the reconfiguration of an existingenclosure, would be superior to the complex hardware identifiers fused,burned, or otherwise permanently associated with most networkedmicrocontrollers and networking peripherals. This application disclosesa system and method for automatically associating sequentialidentification values with the complex and generally nonsequentialhardware or network address identifiers generally used to address thecontrollers of networked modules, networked accessories, and other such“nodes.”

In a first aspect, disclosed is a system for automatically assigningsequential identification values to a plurality of networked nodes. Thesystem includes a host controller operatively interconnected with aplurality of client controllers by a shared, multi-drop communicationsbus. The host controller is further operatively interconnected with afirst controller of the plurality of client controllers by an initialsegment of a daisy-chained, point-to-point communications bus, with eachprevious controller of the plurality of client controllers beingoperatively connected to a subsequent controller of the plurality ofclient controllers by another segment of the point-to-pointcommunications bus. The host controller includes control logic to (i)issue a token to the first of the plurality of client controllers viathe initial segment of the point-to-point communications bus, (ii)following issue of the token, query the plurality of client controllersvia the multi-drop communications bus, (iii) receive a reply via themulti-drop communications bus and, upon receiving the reply, associate areplying client controller with a sequential identification value, and(iv) command via the multi-drop communications bus passing of the tokenvia the point-to-point communications bus. The client controllersinclude control logic to (i) receive the token via the point-to-pointcommunications bus, (ii) receive the query via the multi-dropcommunications bus, (iii) if that controller has the token, issue thereply to the query via the multi-drop communications bus, and (iv)receive the command via the multi-drop communications bus and, if thatcontroller holds the token, pass the token via the point-to-pointcommunications bus to a subsequent controller of the plurality of clientcontrollers.

In a second aspect, disclosed is storage and dispensing enclosureincluding a host controller and a plurality of accessory modules, eachincluding a respective client controller, disposed within the enclosure.The storage and dispensing enclosure also includes a shared, multi-dropcommunications bus operatively interconnecting the host controller withthe plurality of accessory modules via the respective clientcontrollers. The storage and dispensing enclosure further includes adaisy-chained, point-to-point communications bus operativelyinterconnecting the host controller with a first of the plurality ofaccessory modules via an initial segment, and each previous accessorymodule of the plurality of accessory modules being with each subsequentaccessory module of the plurality of accessory modules via additionalsegments. The host controller includes control logic to (i) issue atoken to the first of the plurality of accessory modules via the initialsegment of the point-to-point communications bus, (ii) following issueof the token, query the plurality of accessory modules via themulti-drop communications bus, (iii) receive a reply via the multi-dropcommunications bus and, upon receiving the reply, associate a replyingaccessory module with a sequential identification value, and (iv)command via the multi-drop communications bus passing of the token viathe daisy-chained, point-to-point communications bu. The accessorymodules include control logic to (i) receive the token via thepoint-to-point communications bus, (ii) receive the query via themulti-drop communications bus, (iii) if that accessory module has thetoken, issue the reply to the query via the multi-drop communicationsbus, and (iv) receive the command via the multi-drop communications busand, if that accessory module holds the token, pass the token via thepoint-to-point communications bus to a subsequent accessory module ofthe plurality of accessory modules.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view of a first aspect of a system architecturefor a storage and dispensing enclosure.

FIG. 2 is a schematic view of an exemplary host or master controller foruse with the system architecture shown in FIG. 1 .

FIG. 3 is a schematic view of an exemplary client or slave controllerfor use with the system architecture shown in FIG. 1 .

FIG. 4 is a schematic view of an exemplary physical architecture for astorage and dispensing enclosure.

FIG. 5 is a block diagram illustrating a method of identifying andassigning sequential identification values to client controllers in oneor more storage and dispensing enclosures.

FIG. 6 is an illustration of a prior art system architecture forpoint-to-point data communications, for an exemplary touchscreen videonode, in a storage and dispensing enclosure.

FIG. 7 is an illustration of a second aspect of a system architecturefor a storage and dispensing enclosure that employs serialization withinhigh speed structured cabling for point-to-point communications.

DETAILED DESCRIPTION

In certain processing environments, it is desirable to be able toautomatically assign simple, sequential identification values tonetworked client nodes depending upon the order in which they arephysically connected to a host node via a linear bus. That ability canbe important when functionally random and unique identification numberssuch as Globally Unique Identifiers (GUIDs), Media Access Control (MAC)addresses, or the like must be logically associated with a relativephysical location within a network or device. An example of such anenvironment would be a storage and dispensing disclosure, whereaccessory modules may be installed in various locations within anenclosure frame, and the relative physical location of the accessorymodule within the enclosure frame is the principal distinguishingcharacteristic to a human operator configuring or maintaining thedevice.

In some existing storage and dispensing enclosures, such as vendingmachines, the physical locations of motor and switch elements can belaid out in a fixed X-Y grid topology that is addressable using fixedrow and column wiring. Each element can then be efficiently identifiedand addressed by well-known column and row addressing methods so long asthere is a single input device and/or single output device per node andper-location. That efficiency is lost, however, when complex wiringharnesses begin to be required to support complex input/outputrequirements for multi-functional modules or nodes, when differentlysized accessories begin to be installed in varying locations within anenclosure, and when an enclosure may be configured with differentaccessories having different input/output requirements. For example, acustomer may want a series of enclosures that include fourdifferent-sized compartments in two or more different configurations,and where some of the compartments are both access-controlled andenvironmentally monitored. Grid wiring and fixed wiring harnessesdirectly connected to a central controller are not well-suited for usein such architectures.

Accordingly, in a first aspect schematically illustrated in FIG. 1 , astorage and dispensing enclosure may include a host controller 100. Thehost controller 100 includes control logic stored in a memory such as aread-only memory, a non-volatile and re-writeable memory, or acombination thereof. In some constructions, the control logic of thehost controller 100 may indirectly control access to compartments in thestorage and dispensing unit based upon a payment or an authorization. Insome constructions, the control logic of the host controller 100 mayindirectly control the operation of active dispensing modules based upona payment or an authorization. In some constructions, the control logicof the host controller 100 may monitor events communicated by passivedispensing modules so as to record an indication of a dispensing event.Constructions may include any one or more of the foregoingfunctionalities.

The storage and dispensing enclosure also includes a plurality of clientcontrollers 200, e.g., a first client controller 200 a, a second clientcontroller 200 b, and a third client controller 200 c. Each clientcontroller may have a unique ID 201, e.g., IDs 201 a, 201 b, and 201 c,respectively. The unique ID may be a hardware identifier such as a GUIDor a MAC address, or may be an assigned unique ID such as an IP address.The client controllers 200 also include control logic stored in a memorysuch as a read-only memory, a non-volatile and re-writeable memory, or acombination thereof. For example, a client controller 200 such ascontroller 200 a may, responsive to host controller 100, directlycontrol a door lock so as to control access to a compartment of thestorage and dispensing unit. For further example, a client controllersuch as controller 200 b may, responsive to host controller 100,directly control the operation of an active dispensing module, such as a“pusher,” so as to dispense an item via the active dispensing module.For yet further example, a client controller 200 such as controller 200c may monitor a passive dispensing module, such as a bin resting upon aload cell, and communicate to host controller 100 a dispensing eventwhen the passive dispensing module senses the removal of an item fromthe bin.

The host controller 100 is operatively interconnected with the pluralityof client controllers 200 by a shared, multi-drop communications bus300. The multi-drop communications bus 300 may be, for example, anRS-485-compliant bus. The multi-drop communications bus 300 may be, forexample, a Controller Area Network (CAN)-specification-compliant bus.Other shared, multi-drop communications bus technologies usable with thesystem and method will be readily apparent to those skilled on the art.

The host controller 100 is also operatively connected to a firstcontroller of the plurality of client controllers 200 by a segment ofdaisy-chained, point-to-point communications bus 350. The point-to-pointcommunications bus 350 may be, for example, an RS-422-compliant bus.Other daisy-chainable, point-to-point communications bus technologiesusable with the system and method will also be readily apparent to thoseskilled on the art. The first controller of the plurality of clientcontrollers, e.g., controller 200 a, is operatively connected to asecond of the plurality of client controllers 200, e.g., controller 200b, by a different segment of the daisy-chained, point-to-pointcommunications bus 350, and so on, so that, in general, each previouscontroller of the plurality of client controllers 200 is operativelyconnected to a subsequent controller of the plurality of clientcontrollers 200 by another segment of the daisy-chained, point-to-pointcommunications bus 350. Consequently, the host controller 100 cancommunicate via the multi-drop communications bus 300 with each of theplurality of client controllers 200, but via the point-to-pointcommunications bus 350 with only the first of the plurality of clientcontrollers 200. The first controller of the plurality of clientcontrollers 200 can communicate via the point-to-point communicationsbus 350 with only a controller attached to the same segment, and so on.Preferably, each previous controller of the plurality of clientcontrollers 200 can only transmit via the point-to-point communicationsbus 350 to a subsequent controller of the plurality of clientcontrollers 200.

The host controller 100 includes control logic to issue a token to thefirst of the plurality of client controllers 200 via the point-to-pointcommunications bus 350. The token may be a simple unique number, a datapacket including a token flag or a unique number, or the like. The tokenis used to control the discovery and identification of the plurality ofclient controllers 200 via the multi-drop communications bus 300. Aclient controller 200 that has received and not yet passed on the tokenmay reply to the host controller 100 during commissioning of the system,such as during initial configuration of an enclosure, maintenanceinvolving the replacement of a node in an enclosure, or reconfigurationof the nodes installed in an enclosure. Other client controllers thathave passed on the token, i.e., have been discovered and associated witha sequential identification value, or have not yet received the token,i.e., have not yet been discovered and not yet been associated with asequential identification value, will remain silent. The daisy-chained,point-to-point communications bus 350 and the orderly passing of thetoken along that bus consequently enables sequential identificationvalues to be associated with the plurality of client controllers 200based upon the order in which they are physically connected to the hostcontroller 100 via that bus. The point-to-point communications bus 350may be disposed within the storage and dispensing enclosure in aconfiguration readily observable by a human operator (e.g., by beingvisible from the front or rear of the enclosure, potentially after theremoval of a fascia, panel, or the like), allowing the operator toobserve the sequence in which each node is physically connected to thatbus.

The host controller 100 further includes control logic to, followingissue of the token, query the plurality of client controllers via themulti-drop communications bus 300. Each of the plurality of clientcontrollers 200 includes control logic to receive the token issued viathe point-to-point communications bus 350, to receive the query via themulti-drop communications bus 300, and, if that controller has thetoken, to reply to the query via the multi-drop communications bus 300.The reply to the query may include the unique ID 201 and/or otherinformation such as the type of module controlled by that clientcontroller 200 and the version of the control logic in that clientcontroller 200.

The host controller 100 further includes control logic to receive thereply via the multi-drop communications bus 300, to associate thereplying client controller with a sequential identification value, andto transmit an acknowledgement to the replying client controller via themulti-drop communications bus 300. The host controller may associate thereplying client controller with a sequential identification value byassociating a replying client controller's unique ID 201 with thesequential identification value. However, if the replying clientcontroller does not have a unique ID 201, the host controller mayassociate the replying client controller with a sequentialidentification value by assigning the replying client controller thesequential identification value as a local address on the multi-dropcommunications bus 300. The acknowledgement may include the associatedsequential identification value, which may be stored by the replyingclient controller within a non-volatile and rewritable memory. Thesequential identification value may be used by the replying clientcontroller as its local address on the multi-drop communications bus300. The sequential identification value may also or alternately bedisplayed by the node of the replying client controller as a visibleindication of the associated sequential identification value at thenode. The acknowledgement, whether or not including the associatedsequential identification value, may trigger the replying clientcontroller to set an association status flag within a non-volatile andrewritable memory signifying that the controller has been associatedwith a sequential identification value. The status stored by theassociation status flag may be displayed by the node as a visibleindication of whether the host controller 100 has associated clientcontroller 200 with the sequential identification value. The hostcontroller 100 may subsequently increment a counter to create asubsequent sequential identification value or increment an index toreference a subsequent sequential identification value from a list,array, table, matrix, or other store for a predetermined sequence. Thereader will appreciate that the sequential identification value could bea numerical value (e.g., 1, 2, 3 . . . ), an alphanumerical value (e.g.,value from a hexadecimal sequence), or a value from a predeterminedsequence (for sake of illustration, “first,” “second,” “third” . . . ).

The host controller 100 yet further includes control logic to commandvia the multi-drop communications bus 300 passing of the token (e.g.,transmits a broadcast command to all client controllers 200 for anyhaving the token to pass the token to a subsequent client controller),and each of the plurality of client controllers 200 further includescontrol logic to receive the command via the multi-drop communicationsbus 300 and, if it holds the token, pass the token via thepoint-to-point communications bus 350 to a subsequent controller of theplurality of client controllers 200.

After issuing the command over the multi-drop communication bus 300, thehost controller control logic iterates the querying, receiving,associating, transmitting, and commanding logic until the last of theplurality of client controllers 200 is identified and associated or afault occurs. The host controller 100 may assume completion of thecommissioning (identification and association) process if a reply is notreceived within a timeout. Alternately, the last of the plurality ofclient controllers 200 may send an end-of-bus, negative acknowledgement,or similar message if it has the token and is commanded to pass thetoken, if the point-to-point communications bus 350 has aconnection-sensing capability. Faults may be indicated by theaforementioned display of the node. For example, an alphanumeric displaymay display a character indicating whether the client controller of thenode is in commissioning mode (awaiting receipt of the token) or hasbeen identified and associated (has received and passed on the token).Such a display may also indicate whether a node has the token, which maybe useful for identifying a faulty connection between that clientcontroller 200 and the multi-drop communications bus 300. An alternate,multiple position or multiple color LED display may illuminateparticular LEDs or illuminate particular colors to provide the sameindications.

Turning to FIG. 2 , an exemplary host controller 100 may comprise amicrocontroller or central processing unit 110, a memory 120, a firstbus interface 130 to the multi-drop communications bus 300, and a secondbus interface 140 to the point-to-point communications bus 350. Thememory 120 is preferably non-volatile and rewriteable (so as to serve asa repository for upgradable control logic and the associationinformation described above), but may be volatile random access memorypaired with firmware. In one construction, the first bus interface 130includes a universal asynchronous receiver/transmitter (UART) 132 and anRS-485-compliant transceiver 134. In another construction, the businterface 130 includes a CAN controller 136 and CAN transceiver 138(alternate operative connections shown using broken lines). In theillustrated constructions, the second bus interface 140 includes asecond universal asynchronous receiver/transmitter (UART) 142 and anRS-422-compliant transmitter 144. It will be appreciated that in otherconstructions, the transmitter could be a transceiver and the businterface may not require a UART.

Turning to FIG. 3 , an exemplary client controller 200 may comprise amicrocontroller or central processing unit 210, a memory 220, a firstbus interface 230 to the multi-drop communications bus 300, and a secondbus interface 240 to the point-to-point communications bus 350. Thememory 220 is again preferably non-volatile and rewriteable (so as toserve as a repository for upgradable control logic and the associationinformation described above), but may be volatile random access memorypaired with firmware. In one construction, the first bus interface 230includes a universal asynchronous receiver/transmitter (UART) 232 and anRS-485-compliant transceiver 234. In another construction, the businterface 230 includes a CAN controller 236 and CAN transceiver 238(alternate operative connections shown using broken lines). In theillustrated construction, the second bus interface 240 includes a seconduniversal asynchronous receiver/transmitter (UART) 242 and at least oneRS-422-compliant transceiver 244. In the illustrated construction, asingle RS-422-compliant transceiver receives from a prior segment of thepoint-to-point communications bus 350 and transmits to a subsequentsegment of that bus so that communication through the bus 350 isone-directional. It will be appreciated that in other constructions, atransceiver may provide bidirectional communications, there may bepaired transceivers to connect to the previous and subsequent segments,and the bus interface may require other UARTs or controllers.

Turning to FIG. 4 , a preferred physical construction of the systemcombines the multi-drop communications bus and point-to-pointcommunications bus in twisted pair cabling (e.g., “category 5” orANSI/TIA/EIA-568-A cabling; used pairs are shown as single lines forclarity of illustration). The multi-drop communication bus 300 iscontinuous between input 250 and output 260 ports of each clientcontroller 200/node, with a drop connecting to the first bus interface230 of the node, so that a first wire pair of the cabling forms anuninterrupted bus segment across all connected controllers 100, 200. Thepoint-to-point communication bus 350 is interrupted by the second businterface of the node so that another wire pair, or single wire inone-way implementations of the bus, forms a daisy-chain of interruptedbus segments across all connected controllers 100, 200. Accordingly, alinear bus having an arbitrary shape and length can be formed bydaisy-chaining controllers 100, 200 of the nodes using readily availablestructured cabling.

FIG. 5 summarizes a method 500 reflecting the control logic describedabove. In a system including a host controller 100 and a plurality ofclient controllers 200, with the host controller 100 operativelyconnected to the plurality of client controllers 200 via a multi-dropcommunications bus 300, the host controller 100 operatively connected toa first controller of the plurality of client controllers 200 via asegment of a point-to-point communications bus, and each previouscontroller of the plurality of client controllers 200 operativelyconnected to a subsequent controller of the plurality of clientcontrollers 200 via another segment of the point-to-point communicationsbus 350, a host controller 100 may transmit a commissioning order 510 toa plurality of client controllers 200 via the multi-drop communicationsbus 310. Such a commissioning order may trigger the plurality of clientcontrollers 200 to cease transmitting on the multi-drop communicationsbus, to discard any stored sequential identification value and/or resetany association status flag, and to enter a commissioning mode. Thereader will appreciate that this step is considered optional, since ahost controller 100 and plurality of client controllers 200 may bemanually placed into a commissioning mode or ordered to enter acommissioning mode by other means.

The host controller 100 issues a token 520 to a first controller of theplurality of client controllers via the point-to-point communicationsbus 350. The host controller 100 queries 530 the plurality of clientcontrollers 200 via the multi-drop communications bus 300. A clientcontroller receiving the query and having the token replies 540 to thehost controller 100 via the multi-drop communications bus 300. The hostcontroller 100 receives 550 a the reply, associates 550 b the replyingclient controller with a sequential identification value, andacknowledges 550 c the association to the replying client controller viathe multi-drop communications bus 300. The replying client controller,receiving the acknowledgement and having the token, stores 560 theacknowledgement event. The storage may include storing an associatedsequential identification value, setting an association status flag, ora combination of the foregoing. The host controller 100 and replyingclient controller may optionally use an associated sequentialidentification value as a local address 565 of the replying clientcontroller on the multi-drop communications bus 300, such as when theplurality of client controllers 200 includes client controllers that donot include a pre-assigned unique ID.

The host controller 100 commands 570 via the multi-drop communicationbus 300 passing of the token. The replying client controller, receivingthe command and having the token, passes the token 580 via thepoint-to-point communications bus 350 to a subsequent client controllerof the plurality of client controllers. Then, the steps 520 through 580are repeated. The reader will appreciate that there may be variations ofand additional steps in the method reflecting the options andalternatives described for the control logic above.

The system and method advantageously establish a sequentialidentification value that has a simple and easily comprehended meaningto a human operator, who could be responsible for the initialconfiguration of an enclosure, the in-the-field repair of amalfunctioning enclosure, or the reconfiguration of an existingenclosure. This logical sequential identification value may be used foraddressing client controllers on the multi-drop communications bus 300,but even more importantly may be used by a human operator to, forexample, identify to the host controller 100, or any computer executingpayment, authentication, and/or stock tracking software, the items thathave been stocked in a particular compartment, active dispensing unit,or passive dispensing unit. Other uses for the sequential identificationvalue will be apparent to those working in the art. In contrast to priorsystems and methods, no unique parameters must be loaded when compilingcontroller control logic or manually programmed during initialconfiguration of an enclosure. Once commissioning has been completed,the multi-drop communications bus 300 enables operation even when singleor multiple nodes have failed, while during commissioning theassociation of sequential identification values and potential fordisplay of commissioning status (potentially by display of associationstatus or the associated sequential identification value itself at eachnode) enables ready identification of faulty nodes, defective cablingsegments and the like. Finally, the system and method simplyin-the-field replacement of nodes or reconfiguration of an enclosure.The nodes may be interconnected using inexpensive structured cabling bytechnically savvy but relatively untrained operators, so thatin-the-field replacements may be performed by non-specialized fieldservice technicians and, potentially, an end user's own technical staff.

Structured Cabling Serialization

In another aspect, a system architecture for a storage and dispensingenclosure with complex input/output requirements is disclosed.

FIG. 6 illustrates a prior art system architecture in which a remotenode is directly controlled by a central controller 600. The exemplaryremote node 650 is a touchscreen video interface that illustrates thevariety of input/output interfaces and types that may be required. Theremote node 650 includes audio interface 660 for receiving a digitalaudio signal, such as an I2S interface, a video interface 670 forreceiving a digital video signal, such as an LVDS, HDMI, or Displayportinterface, and an IRQ pin 680 and I2C interface 690 for a touchscreencontroller 692, with additional use of the I2C interface for a videoscreen backlight controller 694. The central controller 600, which maybe a so-called embedded personal computer, correspondingly includes anaudio interface 610, such as an I2S interface, a video interface 670 fortransmitting a digital video signal, such as an HDMI or Displayportinterface, GPIO pin 630 for receiving the output of the touchscreencontroller IRQ pin, and I2C interface 640 connection to the I2Cinterface 690. Each wiring connection between corresponding interfacesrequires cables including at least one and potentially up to 30 wires.Such wiring can be costly and difficult to route within complex andcramped storage and dispensing enclosures, particularly if longerlengths are required.

FIG. 7 shows a system architecture in which the central controller 600includes a plurality of digital interfaces, e.g., the audio interface610, video interface 620, GPIO pin 630 and I2C interface 640, connectedto a first serializer/deserializer 700 local to the central controller.Correspondingly, the remote node 650 includes a plurality of digitalinterfaces connected to a second serializer/deserializer 750 local tothe remote node. The first and second serializer/deserializers areinterconnected by a single cable 710 which may include as few as twowires. The comparatively low data rate audio signal between audiointerfaces 610 and 660, the comparatively high data rate video signalbetween video interfaces 620 and 670, and the other signals betweeninterfaces 630 and 640 and 680 and 690, respectively, are serializedinto a single high data rate signal for transmission within cable 710between the central controller 600 and remote node 650. Such a cable 710may be twisted pair cabling (e.g., “category 5” or ANSI/TIA/EIA-568-Acabling, “category 6” or ANSI/TIA-568-C.1 cabling, or other high speedstructured cabling, including shielded twisted pair cabling). Thisadvantageously substantially reduces the cost, bulk, and routingcomplexity of prior, interface-specific point-to-point cabling withinsuch systems.

Although the invention is shown and described with respect to certainembodiments and constructions, it should be clear that modificationswill occur to those skilled in the art upon reading and understandingthe specification, and the present invention includes all suchmodifications.

1-20. (canceled)
 21. A method for automatically assigning sequentialidentification values to a plurality of networked nodes including a hostcontroller operatively interconnected with a plurality of clientcontrollers by a shared, multi-drop communications bus, the hostcontroller being further operatively interconnected with a firstcontroller of the plurality of client controllers by an initial segmentof a daisy-chained, point-to-point communications bus, and each previouscontroller of the plurality of client controllers being operativelyconnected to a subsequent controller of the plurality of clientcontrollers by another segment of the point-to-point communications bus,the method comprising the steps of: issuing, via the host controller, atoken to a first controller of the plurality of client controllers viathe point-to-point communications bus; querying, via the hostcontroller, the plurality of client controllers via the multi-dropcommunications bus, and receiving, via the host controller, from aclient controller having the token, a reply via the multi-dropcommunications bus; associating, via the host controller, the replyingclient controller with a sequential identification value; acknowledging,via the host controller, the association to the replying clientcontroller via the multi-drop communications bus 300; commanding, viathe host controller and multi-drop communications bus, passing of thetoken to a subsequent controller of the plurality of client controllersvia the point-to-point communications bus; and repeating the querying,associating, acknowledging, and commanding steps.
 22. The method ofclaim 21, further comprising, prior to the issuing step, the step of:transmitting a commissioning order to the plurality of clientcontrollers via the multi-drop communications bus so as to trigger theplurality of client controllers to enter a commissioning mode.
 23. Themethod of claim 21, wherein the associating step comprises associating aunique identifier of the replying client controller with the sequentialidentification value.
 24. The method of claim 23, wherein the uniqueidentifier of replying client controllers are generally nonsequential.25. The method of claim 21, wherein the acknowledging step comprisestransmitting the associated sequential identification value to thereplying client controller.
 26. The method of claim 21, wherein therepeating step comprises repeating the querying, associating,acknowledging, and commanding steps until a reply is not received withina timeout period.
 27. The method of claim 21, wherein the repeating stepcomprises repeating the querying, associating, acknowledging, andcommanding steps until the reply includes a message indicative of theend of the point-to-point communications bus.
 28. The method of claim21, wherein the sequential identification value is a numerical value, analphanumerical value, or a value from a predetermined sequence.
 29. Amethod for automatically assigning sequential identification values to aplurality of networked nodes including a host controller operativelyinterconnected with a plurality of client controllers by a shared,multi-drop communications bus, the host controller being furtheroperatively interconnected with a first controller of the plurality ofclient controllers by an initial segment of a daisy-chained,point-to-point communications bus, and each previous controller of theplurality of client controllers being operatively connected to asubsequent controller of the plurality of client controllers by anothersegment of the point-to-point communications bus, the method comprisingthe steps of: receiving a token, via a controller of the plurality ofclient controllers, via the point-to-point communications bus; receivinga query, via the said controller of the plurality of client controllers,via the multi-drop communications bus; replying to the query, via thesaid controller and the multi-drop communications bus, if the saidcontroller has the token; receiving and storing an acknowledgement, atthe said controller, that the reply to the query has been received bythe host controller; receiving a command, via the said controller andthe multi-drop communications bus, to pass the token; and afterreceiving the command, passing the token, via the said controller andthe point-to-point communications bus, to a subsequent controller of theplurality of client controllers.
 30. The method of claim 29, wherein thesaid controller of the plurality of client controllers has a uniqueidentifier, and the reply to the query includes the unique identifier.31. The method of claim 30, wherein the unique identifiers of theplurality of client controllers are generally non-sequential.
 32. Themethod of claim 31, wherein the unique identifier is an InternetProtocol address.
 33. The method of claim 29, further comprising thestep of entering, via the said client controller after receiving acommissioning order via the multi-drop wireless communications bus, acommissioning mode.
 34. The method of claim 33, wherein entering thecommissioning mode includes a cessation of transmissions by the saidclient controller on the multi-drop communications bus, and discardingany stored sequential identification value and/or resetting anyassociation status flag used by the said client controller.
 35. Themethod of claim 29, wherein receiving and storing the acknowledgementincludes storing an associated sequential identification value, settingan association status flag, or a combination of the foregoing, in thesaid client controller.
 36. The method of claim 35, wherein theassociated sequential identification value is used as a local address ofthe said client controller on the multi-drop communications bus.
 37. Themethod of claim 29, further comprising the steps of sensing that thesaid client controller is a last of the plurality of client controllersalong the point-to-point communications bus and, after receiving thecommand, sending a message indicative of the end of the point-to-pointcommunications bus via the said client controller and the multi-dropcommunications bus.
 38. The method of claim 29, further comprising thestep of displaying, via the said client controller, an indication thatthe said client controller is awaiting receipt of the token or that thesaid client controller has been identified and associated with asequential identification value.
 39. The method of claim 38, wherein theindication that the said client controller has been identified andassociated with a sequential identification value includes thesequential identification value.
 40. The method of claim 29, furthercomprising the step of displaying, via the said client controller, thatthe said client controller has the token.